_____________________________________________________________________________ The following document discusses how to configure NetWare FTAM to communicate with OSI End Systems that do not support ES/IS. NOTE, this is not a certified Novell document. Novell makes no explicit or implied claims to the validity of this information. If there are any discrepancies noted in this file, please post on NetWire to Auston Erwin (CompuServe account number 76702,537) so that the appropriate changes can be made. _____________________________________________________________________________ NetWare FTAM setup for OSI clients that do not support ES/IS routing. PRODUCT: NetWare FTAM VERSION: 1.1, 1.2 ISSUE/PROBLEM: Problems configuring NetWare FTAM to communicate with OSI End Systems that do not support ES/IS. SOLUTION: There are some early implementations of FTAM services using OSI protocol that do not support ES/IS routing. Novell NetWare's FTAM/OSI implementation complies with US GOSIP 1.0. When a NetWare FTAM Server tries to communicate with any client systems, part of the handshake sequence will require advertising our NSAP address as a MULTICAST packet. Unfortunately, not all OSI vendors support ES/IS dynamic routing. Hence, not all OSI clients will recognize the advertised MULTICAST packet, and communication may not be established. The symptom will typically be an FTAM client trying to do a file transfer to a NetWare FTAM Server and get an error messages returned indicating that a network level connection cannot be established. First, you need to verify whether the client system supports ES/IS routing in their underlying OSI protocol. (A typical example of an OSI client that does not support ES/IS routing would be DEC's VOTS/FTAM) Once you have identified that your FTAM client does not support ES/IS routing, you will need to add extra configuration parameters to your NetWare server in the SYS:OSI/OSI.OCF file in order to configure static routing between NetWare FTAM and your FTAM client. 1. Find out the NSAP address of the FTAM client, that does not support ES/IS routing: |<- MAC or SNPA->| eg. 47 00 04 00 01 00 01 AA BB CC DD EE FF 21 (OSINET NSAP) |<------------------NSAP--------------->| 2. Find out the MAC/SNPA address of the FTAM client: eg. AA BB CC DD EE FF 3. Determine what addressing scheme the FTAM client currently is using: eg. OSINET (AFI:47) NSAP address = 47.................. MAP/TOP 2.1(AFI:49) NSAP address = 49.................. U.K. GOSIP (AFI:38) NSAP address = 38.................. U.K. GOSIP (AFI:39) NSAP address = 39.................. 4. Depending on the FTAM client's addressing scheme, add the 4 templates for each OSI client, similiar to the following examples in the SYS:OSI/OSI.OCF file. (a) FTAM client is using OSINET NSAP address (AFI:47) ____________________________________________________ 47 00 04 00 01 00 01 ** ** ** ** ** ** 21 ^47=AFI np_cnfg.lk0_rmflags=0x01; np_cnfg.lk0_template=0x47,0x00,0x04,0x00, 0x01,0x00,0x01,0x00, 0x00,0x00,0x00,0x00, 0x00,0x21; np_cnfg.lk0_adrmask =0xFF,0xFF,0xFF,0xFF, 0xFF,0xFF,0xFF,0x00, 0x00,0x00,0x00,0x00, 0x00,0xFF; np_cnfg.lk0_snpamask=0x00,0x00,0x00,0x00, 0x00,0x00,0x00,0xFF, 0xFF,0xFF,0xFF,0xFF, 0xFF,0x00; (b) When the FTAM client is using MAP/TOP 2.1 NSAP address (AFI:49) ____________________________________________________ 49 00 01 ** ** ** ** ** ** FE 01 ^49=AFI np_cnfg.lk0_rmflags=0x01; np_cnfg.lk0_template=0x49,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0xFE,0x01; np_cnfg.lk0_adrmask =0xFF,0xFF,0xFF,0x00,0x00,0x00,0x00,0x00,0x00,0xFF,0xFF; np_cnfg.lk0_snpamask=0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x00,0x00; (c) When the FTAM client is using U.K. GOSIP NSAP address (AFI:38) ____________________________________________________ 38 82 6F ** ** ** ** ** ** ^38=AFI ^826=defined ^F=padding np_cnfg.lk0_rmflags=0x01; np_cnfg.lk0_template=0x38,0x82,0x6F,0x00,0x00,0x00,0x00,0x00,0x00; np_cnfg.lk0_adrmask =0xFF,0xFF,0xFF,0x00,0x00,0x00,0x00,0x00,0x00; np_cnfg.lk0_snpamask=0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF; (d) When the FTAM client is using U.K. GOSIP NSAP address (AFI:39) ____________________________________________________ 39 82 6* ** ** ** ** ** *F ^38=AFI ^826=defined ^F=padding np_cnfg.lk0_rmflags=0x01; np_cnfg.lk0_template=0x39,0x82,0x60,0x00,0x00,0x00,0x00,0x00,0x0F; np_cnfg.lk0_adrmask =0xFF,0xFF,0xF0,0x00,0x00,0x00,0x00,0x00,0x0F; np_cnfg.lk0_snpamask=0x00,0x00,0x0F,0xFF,0xFF,0xFF,0xFF,0xFF,0xF0; 6. Finally, unload/unbind all OSI/FTAM related services and reload/rebind all OSI/FTAM services to NetWare. 7. Do not temper with any other entries in this osi.ocf file. A sample SYS:OSI/OSI.OCF file is listed below, which allows NetWare FTAM server "47 00 04 00 3C 00 01 00 00 1B 03 75 25 01" to communicate with ANY Vaxes with the following NSAP address of "47 00 04 00 06 00 01 XX XX XX XX XX XX 21". Sample OSI.OCF file: ############################################################################ # # # IMPORTANT NOTICE: This file contains configuration information for # # NetWare OSI. It is created and used by programs. # # DO NOT CHANGE or DELETE THIS FILE, unless you are # # told to do so by NOVELL authorized Support Staff. # # # ############################################################################ ##### local parameters ###### local.server_name="OSD-BERNSTEIN"; local.consoleflag=0; local.nsap=0x47,0x00,0x04,0x00,0x3C,0x00,0x01,0x00,0x00,0x1B,0x03,0x75,0x25, 0x01; ##### resource management parameters ###### socket_init.socket_rcvqta=14336; socket_init.socket_sndqta=8192; ##### lower layers parameters ####### np_cnfg.cp_npflags=0x0; np_cnfg.cp_lifetime=30; np_cnfg.cp_cttime=20; np_cnfg.cp_tmoutesh=300; tp_cnfg.tpc_checksum=0; cltp_cnfg.cp_tpflags=0x0; ##### FTAM server parameters ###### ftamsvr.local_tsel=0x00,0x01; ftamsvr.print_services=1; ftamsvr.print_device="LPT"; ftamsvr.default_dir="FTAM:/FTAMUSER"; ### connection related parameters ### local.numOfSkts=51; ftamsvr.schdlr_con=50; tp_cnfg.tpc_connections=51; ftamsvr.print_queue="PRINTERQ_0"; ftamsvr.print_server="LOCALPRINTSERVER"; # # To communicate with a DEC client # np_cnfg.lk0_rmflags=0x1; np_cnfg.lk0_template=0x47,0x00,0x04,0x00,0x06,0x00,0x01,0x00,0x00,0x00,0x00, 0x00,0x00,0x21; np_cnfg.lk0_adrmask=0xff,0xff,0xff,0xff,0xff,0xff,0xff,0x00,0x00,0x00,0x00, 0x00,0x00,0xff; np_cnfg.lk0_snpamask=0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xff,0xff,0xff,0xff, 0xff,0xff,0x00;